Inconsistent data will confuse local resolvers. I think you've seen that already.
Wade.
Ouch.
Inconsistent data will confuse local resolvers. I think you've seen that already.
Wade. Q:Is it proper to eat cheeseburgers with your fingers? A:No, the fingers should be eaten separately. |
|
Customer service said "that's normal"
I added the other set of servers as third and fourth, seeing if that helps.
--
Drew |
|
warning, make sure a query returns less than 512k
otherwise a LOT of ns based stuff will break if the initial UDP has to jump to tcp to finish the query
|
|
How do I measure that?
--
Drew |
|
example
nslookup -type=MX me.net
then count the characters that return including spaces, ensure the total count is under 512 |
|
That's interesting
drook@drook-desktop:/var/www$ nslookup -type=CNAME cooklikeyourgrandmother.com Okay, there's no CNAME, which is right. But it shows the authoritative server. That seems right. drook@drook-desktop:/var/www$ nslookup -type=A cooklikeyourgrandmother.com That's good, although I would have thought it would have the authoritative server listed. drook@drook-desktop:/var/www$ nslookup -type=CNAME blog.cooklikeyourgrandmother.com The non-authoritative answer is correct, but authoritative is just blank. Shouldn't there be a value there? --
Drew |
|
is it blank or timed out?
|
|
I pasted everything that showed up
If it timed out, it didn't display anything saying so.
--
Drew |
|
Just got word from the guy who's having the problem
He did an nslookup and got the following:
*** Can't find server name for address 192.168.0.1: Non-existent domain --
Drew |
|
his dns server is down
|
|
So his "internal" DNS caching service is horked.
Its burping on the fscked up glue records.
Geebus... You have to get you own DNS server running and then secondary for it. Or just transfer all the root server entries to DNS MADE EASY. Setup an account for DNS Made Easy. Setup all you hosts properly. Transfer it. DNS IS NOT THIS HARD! It just fscking works when you understand it. DNS Made Easy has an interface that is *BY FAR* the best and simplest interface I have seen. No fancy schmancy AJAX or CSS tricks... bare bones and it works. http://www.gregfolke...pics/dnsmadeeasy/ Go through the pics in order... Also notice in the record mgmt the removal etc... It is very simple, but every function needed is there. |
|
"when you understand it" is the problem
I don't know how much "magic" the current host has going on behind the interface they provide. The nameservers pointing to other nameservers for instance. The multiple A records to handle ssh and webmail and etc. etc. etc. And assuming I knew everything about their network, I still don't know which options to select in all those screenshots you put up.
I know this stuff is easy to people who understand it. I know I could learn it. But if it's done right, it's something I should only have to do once every year or so, or when I set up a new site. --
Drew |
|
Re: "when you understand it" is the problem
Oh, you need a *A* record?
Umm "add A record" Oh you need a wild card A record? Umm, "add A record" Oh you need a CNAME for Blogger? Ummm, "add CNAME record" I mean COME ON DREW, stop being oblique. You posted a picture from before with you DNS control panel. Its NOT rocket science. Stopp thinking its tough. DNS is just a frickin query service for a database of records, you ask for a NAME or type of record for the name it gives you back a number or other entried. SIMPLE. Here is the ZONEFILE I created for you from before. uno:/home/drook/bind# cat cooklikeyourgrandmother.com If I can make this from that picture, you can easily make a setup in DNS made Easy. It really *IS* EASY. Stop thinking its "un-learn-able", it *IS* learn-able. If you need hand holding, let be the first ti offer to help you out. DNS is you life blood, if you can;t get reliable DNS from you hosting provider... move it somewhere else. |
|
think he is talking about the actual IP routing to his stuff
all the names in the world dont help if you are not sure what IP it is tied to in the back end
|
|
You are forgetting EDNS.
EDNS has to be working now a day... to get to (ANY) IPV6 stuff.
|
|
yabbut not all large isp's are using sech
rfc sez an ISP MAY use tcp to follow a longish trail that is too long for a udp packet, MAY is not MUST so many a largish ISP dont follow to the tcp stack as I have argued many times with network folks at mickeysoft. Now ipv6 is coming but many folks want to be dead last in that race.
|
|
Re: warning, make sure a query returns less than 512k
Try 512 octets, which is different.
|
|
yup, sorry about that
|