Results 1 to 9 of 9
  1. #1
    Join Date
    May 2001
    Location
    Indiana, Florida
    Posts
    534

    The weirdest problem with domain name I've ever seen !

    Hello,
    I have problem with my customers domain name and as you guys know its hard to explain that the problem is beyond our control.
    Ok. here it is. The customer has a domain name:

    THENORTHENDONLINE.COM

    the domain name expired about 2 weeks ago but she renewed it.
    So the problem is that if you go to WWW.THENORTHENDONLINE.COM it points to IP address 64.247.34.58 - not my server ! Any other host name
    like THENORTHENDONLINE.COM , MAIL.THENORTHENDONLINE.COM , FTP.THENORTHENDONLINE.COM
    points to proper IP 64.191.7.107

    This is not DNS set up problem, here is DNS zone:

    ---------------------------
    ; WwwAcct 2.5
    ; Zone file for thenorthendonline.com
    @ 14400 IN SOA ns1.vipsnet.com. root.indiana.vipsnet.com. (
    1024690002 ; serial, todays date+todays
    28800 ; refresh, seconds
    7200 ; retry, seconds
    3600000 ; expire, seconds
    86400 ) ; minimum, seconds

    thenorthendonline.com. 14400 IN NS ns1.vipsnet.com.
    thenorthendonline.com. 14400 IN NS ns2.vipsnet.com.
    thenorthendonline.com. 14400 IN A 64.191.7.107

    localhost.thenorthendonline.com. 14400 IN A 127.0.0.1

    thenorthendonline.com. 14400 IN MX 0 thenorthendonline.com.

    mail 14400 IN CNAME thenorthendonline.com.
    www 14400 IN CNAME thenorthendonline.com.
    ftp 14400 IN CNAME thenorthendonline.com.
    ---------------------------------------

    But that's NOTHING. So we have removed DNS servers completely!

    ---------------------------------------------
    Whois Server Version 1.3

    Domain names in the .com, .net, and .org domains can now be registered
    with many different competing registrars. Go to http://www.internic.net
    for detailed information.

    Domain Name: THENORTHENDONLINE.COM
    Registrar: TUCOWS, INC.
    Whois Server: whois.opensrs.net
    Referral URL: http://www.opensrs.org
    Name Server: No nameserver
    Updated Date: 13-jul-2002


    >>> Last update of whois database: Sun, 14 Jul 2002 04:53:06 EDT <<<

    The Registry database contains ONLY .COM, .NET, .ORG, .EDU domains and
    Registrars.
    ---------------------------------------------

    NOTHING has changed ! Domain name and trace routes still go to the IP 64.247.34.58 (only www.thenorthendonline.com), if you try thenorthendonline.com it doesn't work and that's good.

    1 b06sr1-6 (129.186.6.251) 1 ms 0 ms 1 ms
    2 b11sr1-lan255-8.tele.iastate.edu (129.186.255.10) 0 ms 1 ms 0 ms
    3 b31gb1-lan254-128.tele.iastate.edu (129.186.254.131) 0 ms 1 ms 0 ms
    4 b31br4.gw.iastate.edu (192.245.179.130) 0 ms 1 ms 0 ms
    5 ICN-ISU-oc3.icn.state.ia.us (205.221.255.5) 2 ms 2 ms 2 ms
    6 ICN-ISP1.icn.state.ia.us (207.28.254.1) 1 ms 2 ms 1 ms
    7 12.125.74.17 (12.125.74.17) 14 ms 14 ms 13 ms
    8 gbr6-p80.sl9mo.ip.att.net (12.123.24.238) 14 ms 14 ms 14 ms
    9 tbr2-p013501.sl9mo.ip.att.net (12.122.11.121) 15 ms 16 ms 15 ms
    10 12.122.10.89 (12.122.10.89) 55 ms 34 ms 30 ms
    11 12.122.12.78 (12.122.12.78) 28 ms 28 ms 27 ms
    12 gar1-p360.dlstx.ip.att.net (12.123.16.233) 29 ms 28 ms 27 ms
    13 gar1-p340.dlrtx.ip.att.net (12.123.196.97) 28 ms 28 ms 27 ms
    14 att-gw.dal.wcg.net (192.205.32.254) 56 ms 55 ms 54 ms
    15 dllstx1wcx2-oc48.wcg.net (64.200.110.81) 55 ms 55 ms 55 ms
    16 64.200.232.126 (64.200.232.126) 56 ms 55 ms 55 ms
    17 hrndva1wcx2-oc48.wcg.net (64.200.95.73) 55 ms 54 ms 55 ms
    18 nycmny2wcx2-oc48.wcg.net (64.200.240.45) 61 ms 61 ms 61 ms
    19 nycmnyhlce1-oc12.wcg.net (64.200.87.114) 61 ms 61 ms 60 ms
    20 nycmny2lce1-netaccess-atm.wcg.net (64.200.86.150) 94 ms 94 ms 93 ms
    21 a9-0-0-1066.msfc1.oct.nac.net (209.123.11.245) 96 ms 96 ms 95 ms
    22 core1.dcjn.pwebtech.com (209.123.182.242) 97 ms 96 ms 96 ms
    23 64.247.34.58 (64.247.34.58) 99 ms 96 ms 96 ms


    I have just checked few traceroutes from www.traceroute.org.

    Have you ever experienced such thing?

    I have sent email to OpenSRS but got no reply.

    Do you know whats going on?

  2. #2
    How long ago did the client remove the nameservers from her domain?

  3. #3
    Join Date
    May 2001
    Location
    Indiana, Florida
    Posts
    534
    yesterday she has removed the nameservers, but the problem exist for alomost 2 weeks.

    before we had our nameservers ns1/ns2.vipsnet.com with the proper dns zone

    so it cannot be the problem of propagation

  4. #4
    Join Date
    May 2001
    Location
    Indiana, Florida
    Posts
    534
    ah, i forgot to tell, she has 2 more domains which works prefectly fine... just this one doesn't (it expired and she renewed it, maybe at renewal time something happend)

  5. #5
    Join Date
    Dec 2000
    Location
    Scotland
    Posts
    134
    Hiya,

    This little gem again, it confused the hell out of me the first time I saw it.

    www.thenorthendline.com is registered as a nameserver.

    Because of this, there is a seperate A record in the root servers for it.

    From whois:

    tony@echo:~$ whois www.thenorthendonline.com
    [whois.internic.net]

    Whois Server Version 1.3

    Domain names in the .com, .net, and .org domains can now be registered
    with many different competing registrars. Go to http://www.internic.net
    for detailed information.

    Server Name: WWW.THENORTHENDONLINE.COM
    IP Address: 64.247.34.58
    Registrar: TUCOWS, INC.
    Whois Server: whois.opensrs.net
    Referral URL: http://www.opensrs.org


    >>> Last update of whois database: Sun, 14 Jul 2002 04:53:06 EDT <<<


    You need to have the nameserver entry dropped by opensrs (or updated to the correct ip), but dropping it is the best option.

    Once this is done, it will all magically work again.
    Founder & SVP Product
    Flexiant Ltd
    Simplifying the Cloud - Designed for Service Providers
    http://www.flexiant.com

  6. #6
    Just to be sure, if the client doesn't mind waiting, give the domain another 48 hours to propagate - hopefully you get some kind of error when accessing the site. Then, have her add your nameservers back, and wait another 72 hours for that to propagate.

    Also, compare zone files of her other domains that work, with this one and see if there's anything different about them.

  7. #7
    You can remove this "nameserver" entry from the Domain Manager interface at OpenSRS. You don't need to have OpenSRS technical support do this on Monday.

    Log into the manage.opensrs.net interface and go into the nameserver area - remove the nameserver that has been created for this domain and you are all set.

    Changes are sent to Verisign almost immeditely, and Verisign updates the root files twice a day. TTL values in the root are set o 48 hours, so your dat may be cached that long.

    -t
    myOstrich Internet - OpenSRS Domain Names & Digital Certificates
    http://www.myostrich.net

  8. #8
    Originally posted by loopforever
    Just to be sure, if the client doesn't mind waiting, give the domain another 48 hours to propagate ...
    This bogus nameserver is clearly defined in the root files, so you will need to remove it. Waiting will do nothing - as the nameserver was created at OpenSRS and loaded into the root zone. It needs to be removed.

    -t
    myOstrich Internet - OpenSRS Domain Names & Digital Certificates
    http://www.myostrich.net

  9. #9
    Join Date
    May 2001
    Location
    Indiana, Florida
    Posts
    534
    you guys are awesome...
    thewitt, i didn't notice that she created www.thenorthendonline.com as nameserver... i don't have access to OpenSRS manager thats why. I'm gonna email her right now and ask her to remove NS record and enter our nameservers.

    Thanks for your time

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •