Skip to main content

domain name system - DNS failing to propagate worldwide

itemprop="text">

I haven't changed
anything related to the DNS entry for
serverfault.com
, but some users were reporting today that href="https://meta.stackexchange.com/questions/7070/serverfault-down-how-to-get-into-superuser-beta/7079#7079">the
serverfault.com DNS fails to resolve for
them.



I ran a href="http://just-ping.com/index.php?vh=serverfault.com&c=&s=ping!"
rel="nofollow noreferrer">justping query and I can sort of confirm this --
serverfault.com dns appears to be failing to resolve in a handful of countries, for no
particular reason that I can discern. (also confirmed via href="http://www.whatsmydns.net/" rel="nofollow noreferrer">What's My DNS
which does some worldwide pings in a similar fashion, so it's confirmed as an issue by
two different sources.)




href="https://i.stack.imgur.com/pu7UO.png" rel="nofollow noreferrer"> src="https://i.stack.imgur.com/pu7UO.png"
alt>




  • Why
    would this be happening, if I haven't touched the DNS for serverfault.com
    ?


  • our registrar is (gag) GoDaddy, and
    I use default DNS settings for the most part without incident. Am I doing something
    wrong? Have the gods of DNS forsaken
    me?


  • is there anything I can do to fix
    this? Any way to goose the DNS along, or force the DNS to propagate correctly
    worldwide?




Update:
as of Monday at 3:30 am PST, everything looks correct.. JustPing reports site is
reachable from all locations. Thank you for the many very informative responses, I
learned a lot and will refer to this Q the next time this
happens..



itemprop="text">
class="normal">Answer



This is
not directly a DNS problem, it's a network routing problem between some parts of the
internet and the DNS servers for serverfault.com. Since the nameservers can't be reached
the domain stops resolving.



As far as I can tell
the routing problem is on the (Global Crossing?) router with IP address
204.245.39.50.



As href="https://serverfault.com/questions/42678/dns-failing-to-propagate-worldwide/42686#42686">shown
by @radius, packets
to ns52 (as used by href="http://stackoverflow.com">stackoverflow.com) pass from here to
208.109.115.121 and from there work correctly. However packets
to ns22 go instead to
208.109.115.201.



Since
those two addresses are both in the same /24 and the
corresponding BGP announcement is also for a /24 this
shouldn't happen.



I've done
traceroutes via my network which ultimately uses MFN Above.net instead of Global
Crossing to get to GoDaddy and there's no sign of any routing trickery below the
/24 level - both name servers have identical traceroutes from
here.




The only times I've ever seen
something like this it was broken href="http://en.wikipedia.org/wiki/Cisco_Express_Forwarding" rel="nofollow
noreferrer">Cisco Express Forwarding (CEF). This is a hardware level cache
used to accelerate packet routing. Unfortunately just occasionally it gets out of sync
with the real routing table, and tries to forward packets via the wrong interface. CEF
entries can go down to the /32 level even if the underlying
routing table entry is for a /24. It's tricky to find these
sorts of problems, but once identified they're normally easy to
fix.



I've e-mailed GC and also tried to speak to
them, but they won't create a ticket for non-customers. If any of you
are a customer of GC, please try and report
this...



UPDATE at 10:38
UTC
As Jeff has noted the problem has now cleared. Traceroutes to both
servers mentioned above now go via the 208.109.115.121 next
hop.


Comments

Popular posts from this blog

linux - iDRAC6 Virtual Media native library cannot be loaded

When attempting to mount Virtual Media on a iDRAC6 IP KVM session I get the following error: I'm using Ubuntu 9.04 and: $ javaws -version Java(TM) Web Start 1.6.0_16 $ uname -a Linux aud22419-linux 2.6.28-15-generic #51-Ubuntu SMP Mon Aug 31 13:39:06 UTC 2009 x86_64 GNU/Linux $ firefox -version Mozilla Firefox 3.0.14, Copyright (c) 1998 - 2009 mozilla.org On Windows + IE it (unsurprisingly) works. I've just gotten off the phone with the Dell tech support and I was told it is known to work on Linux + Firefox, albeit Ubuntu is not supported (by Dell, that is). Has anyone out there managed to mount virtual media in the same scenario?

hp proliant - Smart Array P822 with HBA Mode?

We get an HP DL360 G8 with an Smart Array P822 controller. On that controller will come a HP StorageWorks D2700 . Does anybody know, that it is possible to run the Smart Array P822 in HBA mode? I found only information about the P410i, who can run HBA. If this is not supported, what you think about the LSI 9207-8e controller? Will this fit good in that setup? The Hardware we get is used but all original from HP. The StorageWorks has 25 x 900 GB SAS 10K disks. Because the disks are not new I would like to use only 22 for raid6, and the rest for spare (I need to see if the disk count is optimal or not for zfs). It would be nice if I'm not stick to SAS in future. As OS I would like to install debian stretch with zfs 0.71 as file system and software raid. I have see that hp has an page for debian to. I would like to use hba mode because it is recommend, that zfs know at most as possible about the disk, and I'm independent from the raid controller. For us zfs have many benefits,

apache 2.2 - Server Potentially Compromised -- c99madshell

So, low and behold, a legacy site we've been hosting for a client had a version of FCKEditor that allowed someone to upload the dreaded c99madshell exploit onto our web host. I'm not a big security buff -- frankly I'm just a dev currently responsible for S/A duties due to a loss of personnel. Accordingly, I'd love any help you server-faulters could provide in assessing the damage from the exploit. To give you a bit of information: The file was uploaded into a directory within the webroot, "/_img/fck_uploads/File/". The Apache user and group are restricted such that they can't log in and don't have permissions outside of the directory from which we serve sites. All the files had 770 permissions (user rwx, group rwx, other none) -- something I wanted to fix but was told to hold off on as it wasn't "high priority" (hopefully this changes that). So it seems the hackers could've easily executed the script. Now I wasn't able