Problem to access to www.mydomain.net

[Kevin Darcy]

Stromboli wrote:

> Hi People!,
> This is my first post to this group and is because I have a proplem
> with DNS. It would be nice if any of you have a clue of what happens.
> I have a dedicated server and I use everydns.net nameservers.
> I've delegated mydomain.com and I can access to ioeie.mydomain.com
> (the IPs for *.mydomain.net were correct) but I can't to
> www.mydomain.net (IP and domain are examples)
>
> I checked and it was because I have written wrong the A record for
> www.mydomain.net.       86400   A       76.139.71.141
> I rewrote it to the correct address
> www.mydomain.net.       86400   A       76.139.73.141
>
> My Http.conf shows
> <VirtualHost 76.139.73.141>
>   ServerName www.mydomain.net
>     ServerAlias mydomain.net *.mydomain.net
> DocumentRoot /home/www/html
> </VirtualHost>
>
> I added a CNAME entry to see if it worked but I still can't access.
> All this happened yesterday and today.
> www.mydomain.net  cname mydomain.net
>
> When I do a ping I still see the old IP but when I run DNSExpert I see
> the correct info. Is just a problem of time of there's something more?
> If it's just the update, how long does it take to change? Is it right
> to add a CNAME entrey for www.mydomain.net if I already have an A
> entry www.mydomain.net --> IP ?
> thanks for your help!, :)
> strom
>
> Ps. below is some info about mydomain
>
> Query: www.mydomain.net.        Query type: Any record
> Recursive query: Yes    Authoritative answer: Yes
> Query time: 1262 ms.    Server name: n/a
>
> Answer:
>         www.mydomain.net.       86400   A       76.139.73.141
>
> Authority:
>         mydomain.net.   86400   NS      ns1.everydns.net.
>         mydomain.net.   86400   NS      ns2.everydns.net.
>         mydomain.net.   86400   NS      ns3.everydns.net.
>         mydomain.net.   86400   NS      ns4.everydns.net.
>
> Additional:
>         ns1.everydns.net.       86400   A       209.75.39.141
>         ns2.everydns.net.       86400   A       209.75.39.142
>         ns3.everydns.net.       86400   A       193.109.122.204
>         ns4.everydns.net.       86400   A       12.25.235.40
>
> --------------------------------------------------------------
> Query: mydomain.net.    Query type: Any record
> Recursive query: Yes    Authoritative answer: Yes
> Query time: 2033 ms.    Server name: n/a
>
> Answer:
>         mydomain.net.   2560    SOA     ns1.everydns.net.
>                                 hostmaster.mydomain.net.
>                                 1034865667      ; serial
>                                 16384   ; refresh (4 hours, 33 minutes, 4 seconds)
>                                 2048    ; retry (34 minutes, 8 seconds)
>                                 1048576 ; expire (12 days, 3 hours, 16 minutes, 16 seconds)
>                                 2560    ; minimum (42 minutes, 40 seconds)
>         mydomain.net.   86400   NS      ns1.everydns.net.
>         mydomain.net.   86400   NS      ns2.everydns.net.
>         mydomain.net.   86400   NS      ns3.everydns.net.
>         mydomain.net.   86400   NS      ns4.everydns.net.
>         mydomain.net.   86400   A       76.139.73.141
>
> Additional:
>         ns1.everydns.net.       86400   A       209.75.39.141
>         ns2.everydns.net.       86400   A       209.75.39.142
>         ns3.everydns.net.       86400   A       193.109.122.204
>         ns4.everydns.net.       86400   A       12.25.235.40

Your TTL is set to a day, so even if nothing is broken, it could take that long for the change
to be visible everywhere.

If it's still wrong after a day, then a couple of possibilities come to mind:

1) You forgot to increment the serial number, so one or more slaves of the zone are still
serving up stale data.

2) The name in question (which you obscured, grrrrrrr) happens to be the name of a nameserver
and there is a stale "glue" record in the gTLD zone.


- Kevin