Announcement
Collapse
No announcement yet.
Welcome to the Cafe!
Collapse
X
-
Propogation of change of an FQDN was my particular gripe at the time.
What really bugged me about it was that if I used an online nslookup tool and told it to use 8.8.8.8 as the ns, it came back with the correct/new ip. If I used 8.8.8.8 locally from my computer or my router, it still had the old IP. I had to update to use Open DNS as my primary to get a few of my tools online and working before the weekend.
Oh well. New week!
Comment
-
Originally posted by LordTrychon View PostPropogation of change of an FQDN was my particular gripe at the time.
What really bugged me about it was that if I used an online nslookup tool and told it to use 8.8.8.8 as the ns, it came back with the correct/new ip. If I used 8.8.8.8 locally from my computer or my router, it still had the old IP. I had to update to use Open DNS as my primary to get a few of my tools online and working before the weekend.
Oh well. New week!
I usually prime my DNS records well before any upcoming changes by changing the TTL to a low value (like 3600s). That way changes happen very quickly. When you're done with your DNS changes you can reset the TTL to it's original value. Of course, that's when you have the luxury of planning and sometimes you don't and then it just stinks.
Comment
-
Originally posted by Rastic View PostDNS propagation, my fav!
I usually prime my DNS records well before any upcoming changes by changing the TTL to a low value (like 3600s). That way changes happen very quickly. When you're done with your DNS changes you can reset the TTL to it's original value. Of course, that's when you have the luxury of planning and sometimes you don't and then it just stinks.
In the end, it worked out, and hopefully I don't have to worry about this particular issue for a few years. *knock on wood*.
Comment
-
Originally posted by LordTrychon View PostWell, I had a few weeks, but I'm not sure I could have really helped myself too much. Networking stuff is really not my wheelhouse. Of course, that's the downside to being jack of all trades.... What really surprised me is that 8.8.8.8 was returning different values depending on where I asked.
In the end, it worked out, and hopefully I don't have to worry about this particular issue for a few years. *knock on wood*.DNS can be frustrating for sure.
Glad it all worked out in the end :thumb:
Edit: never mind, they are in a routed environment. Per Wikipedia, "The addresses are mapped to the nearest operational server by anycast routing."
That at least explains the different results.Last edited by Rastic; 09-05-2017, 08:49 AM.
Comment
-
Originally posted by Rastic View PostYeah, I'm not exactly sure how Google manages their DNS servers. On the surface it sounds like they might be clustered or load-balanced or something similar that would cause different results from querying the same address. Though you'd expect parity to be betterDNS can be frustrating for sure.
Glad it all worked out in the end :thumb:
Edit: never mind, they are in a routed environment. Per Wikipedia, "The addresses are mapped to the nearest operational server by anycast routing."
That at least explains the different results.
How are you?
Comment
-
Originally posted by Jaws View PostWhat's DNS - is it like Do Not Serve?
If it is, not good, especially in a cafe.
DNS also does mean Do not serve though, and that is very bad in the Cafe.
Comment
-
Originally posted by Jaws View PostWhat's DNS - is it like Do Not Serve?
If it is, not good, especially in a cafe.Originally posted by LordTrychon View PostIn this conversation, it was Domain Name Server. It's how computers/modems/etc. look up where to reach websites (to put it simply). Rastic could probably explain it better than I could. To get to the forum, 'forums.denverbroncos.com' has to be translated to an IP address so the request goes to the right server. Domain Name Servers keep track of where those names should point.
DNS also does mean Do not serve though, and that is very bad in the Cafe.
Both would be bad in a cafe.
In this case, just as LT said, it means Domain Name Servers. Think of it like DNS is to internet addresses as the phone book (remember those?) is phone numbers. Each routes something to an address: DNS is a network phone book that translates forums.denverbroncos.com in to it's server address the same as looking up John Q. Public in the phone book can tell me his phone number.
Comment
-
Originally posted by LordTrychon View PostIn this conversation, it was Domain Name Server. It's how computers/modems/etc. look up where to reach websites (to put it simply). Rastic could probably explain it better than I could. To get to the forum, 'forums.denverbroncos.com' has to be translated to an IP address so the request goes to the right server. Domain Name Servers keep track of where those names should point.
DNS also does mean Do not serve though, and that is very bad in the Cafe.
Now I'd like an Irish : coffee: just to make sure there are no serving bans here
Comment
-
Originally posted by Jaws View PostThanks for the explanation
Now I'd like an Irish : coffee: just to make sure there are no serving bans here
That's the day I met Mr. Jameson. It was like someone punched me in the throat and I didn't even have the pleasure of seeing it coming.
Coffee is good. Jameson is good. The two should never get together and just stay friends.
Comment
-
Originally posted by Rastic View PostOMG, that just reminded me of a story. When I was younger I was out with friends at a pretty snazzy restaurant. After dinner I decided to get some coffee. Irish coffee! Yum! Baileys!
That's the day I met Mr. Jameson. It was like someone punched me in the throat and I didn't even have the pleasure of seeing it coming.
Coffee is good. Jameson is good. The two should never get together and just stay friends.
Comment
Comment