Link to home
Start Free TrialLog in
Avatar of maximjon
maximjon

asked on

DNS issue

Hello,

I think I may have an internal DNS caching issue going on.  I just recently changed the name servers to GoDaddy on this domain name we own.  The prior DNS records had the host A records for the website pointing to "Hosting Provider A".  I changed this so that it now points to the new website hosted on "Hosting Provider B".
When I enter this domain address into a browser outside of my company's network, it works fine and brings up the new site on "Hosting Provider B".  However, if I'm inside of my company's network and I put the domain address into a browser, it still takes me to the old site on "Hosting Provider A".
I've flushed my DNS and looked through DNS on our Windows DNS servers but I can't find anything that references the old hosting provider.
If I edit my computers host file and hard code that domain name with "Hosting Provider B"'s address, it works fine but I can't do that for every computer in the company.  Plus that can't be a good solution.
Does anyone else have any suggestions or anywhere else I should check?
Thanks
ASKER CERTIFIED SOLUTION
Avatar of Aard Vark
Aard Vark
Flag of Australia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
it seems issue with in your internal DNS network only,

Run nslookup xxx.com and check with IP you are getting, its from old provider or new provider. it will give you from old provider only.

you have to check you DNS records in your DNS server, check your forwarder zone >>XXX(your site name) check all the records under it.

if you find it then delete and create or modify it with you IP.

wait for 30 mins & check from your system.,...Please update result...what ever it is.
Avatar of maximjon
maximjon

ASKER

Learnctx, this is what the results of the nslookup brings me:

U:\>nslookup -debug www.webdomain.com
------------
Got answer:
    HEADER:
        opcode = QUERY, id = 1, rcode = NOERROR
        header flags:  response, auth. answer, want recursion, recursion avail.
        questions = 1,  answers = 1,  authority records = 0,  additional = 0

    QUESTIONS:
        181.10.168.192.in-addr.arpa, type = PTR, class = IN
    ANSWERS:
    ->  181.10.168.192.in-addr.arpa
        name = mcwdc1.mydomain.com
        ttl = 1200 (20 mins)

------------
Server:  mcwdc1.mydomain.com
Address:  192.168.10.181

------------
Got answer:
    HEADER:
        opcode = QUERY, id = 2, rcode = NXDOMAIN
        header flags:  response, auth. answer, want recursion, recursion avail.
        questions = 1,  answers = 0,  authority records = 1,  additional = 0

    QUESTIONS:
        www.webdomain.com.mydomain.com, type = A, class = IN
    AUTHORITY RECORDS:
    ->  mydomain.com
        ttl = 3600 (1 hour)
        primary name server = mcwdc1.mydomain.com
        responsible mail addr = admin
        serial  = 1883771
        refresh = 3600 (1 hour)
        retry   = 600 (10 mins)
        expire  = 86400 (1 day)
        default TTL = 3600 (1 hour)

------------
------------
Got answer:
    HEADER:
        opcode = QUERY, id = 3, rcode = NXDOMAIN
        header flags:  response, auth. answer, want recursion, recursion avail.
        questions = 1,  answers = 0,  authority records = 1,  additional = 0

    QUESTIONS:
        www.webdomain.com.mydomain.com, type = AAAA, class = IN
    AUTHORITY RECORDS:
    ->  mydomain.com
        ttl = 3600 (1 hour)
        primary name server = mcwdc1.mydomain.com
        responsible mail addr = admin
        serial  = 1883771
        refresh = 3600 (1 hour)
        retry   = 600 (10 mins)
        expire  = 86400 (1 day)
        default TTL = 3600 (1 hour)

------------
------------
Got answer:
    HEADER:
        opcode = QUERY, id = 4, rcode = NOERROR
        header flags:  response, want recursion, recursion avail.
        questions = 1,  answers = 2,  authority records = 0,  additional = 0

    QUESTIONS:
        www.webdomain.com, type = A, class = IN
    ANSWERS:
    ->  www.webdomain.com
        canonical name = webdomain.com
        ttl = 3126 (52 mins 6 secs)
    ->  webdomain.com
        internet address = 50.87.230.94
        ttl = 3126 (52 mins 6 secs)

------------
Non-authoritative answer:
------------
Got answer:
    HEADER:
        opcode = QUERY, id = 5, rcode = NOERROR
        header flags:  response, want recursion, recursion avail.
        questions = 1,  answers = 1,  authority records = 1,  additional = 0

    QUESTIONS:
        www.webdomain.com, type = AAAA, class = IN
    ANSWERS:
    ->  www.webdomain.com
        canonical name = webdomain.com
        ttl = 3126 (52 mins 6 secs)
    AUTHORITY RECORDS:
    ->  webdomain.com
        ttl = 3510 (58 mins 30 secs)
        primary name server = dns1.orlantech.net
        responsible mail addr = hostmaster.orlantech.net
        serial  = 54
        refresh = 3600 (1 hour)
        retry   = 1800 (30 mins)
        expire  = 86400 (1 day)
        default TTL = 3600 (1 hour)

------------
Name:    webdomain.com
Address:  50.87.230.94
Aliases:  www.webdomain.com
Yogeshnmakwana, I've checked multiple times and was unable to find any entries on our DNS server
OK so looking at the debug info from nslookup, TTL does not appear to be an issue at 60 minutes. I'm assuming you're running AD for your internal DNS servers. Some questions about your DC DNS configuration.

Your DC looks to itself and another DC as its configured DNS servers in the connection settings?
Do you have any forwarders or root hints on your DC?
Do you have a DNS zone for your external site on your DC?
Do you have any conditional forwarders configured for the domain in question?

Assuming all of the above checks out, do the same nslookup -debug check from your DC. Do you get the same result back?
Everything internally ended up resolving correctly about an hour after I made my last post