I'll check that out. Thanks for reminding me of this command because I couldn't remember or find it.<br><br>However, in the case of the domain in question, it'll return their SOA records since I couldn't move the domain from their NS to ours.<br>
<br>It may be useful to check other domains, though.<br><br>Sasha<br><br><div class="gmail_quote">On Thu, Jul 2, 2009 at 11:37 AM, Leen Besselink <span dir="ltr"><<a href="mailto:leen@consolejunkie.net">leen@consolejunkie.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">On Thu, Jul 02, 2009 at 06:15:44PM +0300, Jani Karlsson wrote:<br>
> Hi,<br>
><br>
> Your problem is with SOA DNS-record:<br>
> The given nameservers return different SOA entries.<br>
><br>
> So either your SOA serial, data or TTL differs between servers. Or it<br>
> just that other server doesn't respond to SOA request that is making the<br>
> SOA check fail, even though the problem is not with SOA but in that the<br>
> nameserver isn't responding (common GoDaddy error), blaims SOA missing<br>
> or faulty when actually the problem is that the nameserver isn't responding.<br>
><br>
> I hope this clears things a bit.<br>
><br>
<br>
</div>Hi SashaB,<br>
<br>
If you want to lookup the SOA-record of a domain, you could use the 'dig'<br>
command:<br>
<br>
dig @nameserver domain.tld SOA<br>
<br>
But if those are not the same, maybe the domain-zone is not a copy of the<br>
zone on the other nameserver, which is asking for trouble if it's not just<br>
a version difference.<br>
<div><div></div><div class="h5"><br>
> Cheers,<br>
><br>
> Jani Karlsson<br>
><br>
><br>
> SashaB wrote:<br>
> >Ken,<br>
> ><br>
> >I'm not sure what you mean. For example, so we didn't have to enter<br>
> >different NS for 50 domains, I registered a domain name specifically for<br>
> >use with NS (that is their sole purpose) and I've set up NS for multiple<br>
> >website domain names that are identical--kinda like a webhosting company<br>
> >does? There are four NS on two different servers at two datacenters in<br>
> >different parts of a region (for which I haven't mirrored or set up<br>
> >round-robin yet, though I intend to do so--and research shows I can on<br>
> >pdns). Actually, two of the NS point to the same IP address as does the<br>
> >one in question and several other NS point to that IP, too. All server<br>
> >diffent content--blogs, websites, web interfaces for pdns, web guis for<br>
> >various applications, webmail servers--just fine.<br>
> ><br>
> >This works, in part, because the actual content is served, in most<br>
> >cases, though not all, from an entirely different IP addresses from the<br>
> >NS IP addresses (and the virtual host settings on apache reflect that).<br>
> >Yet, we have no problem reaching any of that content, even where the NS<br>
> >IP address are shared with content-serving hostnames rather than<br>
> >dedicated only to doing NS resolution like other IP addresses. Again,<br>
> >domain resolution isn't only about the nameservers--it's about the hosts<br>
> >and host.conf files, as well as whatever backends we use, too. (There<br>
> >are some other factors, like resolvers, but you get my point.)<br>
> ><br>
> >So, as I explained, my mail/webmail NS are on different IP addresses<br>
> >under its domain name from the content the webmail server and mail<br>
> >server 'serves'. All DNS records for the domain are contained on its<br>
> >master server, including both NS, which point back to those IP<br>
> >addresses. The secondary NS has it's own master record on the server<br>
> >where it's located and contains only its IP address, since pdns doesn't<br>
> >use "pointer" records, relying instead on it's native ability to resolve<br>
> >properly configured DNS.<br>
> ><br>
> >Since I've created an "A" record for those IP addresses from which<br>
> >actual content is served in the DNS records on our registrar's site (and<br>
> >have properly configured the vhosts in apache), when we enter either our<br>
> >webmail server IP address or its hostname, my webmail server software<br>
> >admin page loads--just like it should.<br>
> ><br>
> >When I load up the gui interface for our mailserver under either the<br>
> >hostname, which is something like "mailservertype.maildomain.eu", it<br>
> >loads perfectly. This stuff's fairly idiot proof because apache, mysql<br>
> >and pdns all let you know when you've misconfigured stuff by not working<br>
> >right--or at all.<br>
> ><br>
> >Therefore, I don't know how your answer relates to my problem and it<br>
> >doesn't address the issue of the registrar not being able to reach the<br>
> >secondary NS, which is on an entirely different server and has a<br>
> >separate IP address. This doesn't appear, as you suggested when I posted<br>
> >my last question about how PDNS works differently from BIND and again in<br>
> >this post, as my lack of understanding DNS. I'm new to PDNS, not to DNS.<br>
> >I couldn't have set this system up if I didn't have DNS understanding<br>
> >and the registrar for my other domain names seems to have no problem<br>
> >adding our changed NS to their system, so, our NS configuration aren't<br>
> >the problem.<br>
> ><br>
> >If anyone else has any suggestions--especially those in the EU where<br>
> >this seems to be an issue--at least when I bing(.com) it, I would<br>
> >greatly appreciate your help.<br>
> ><br>
> >Sasha<br>
> ><br>
> >On Thu, Jul 2, 2009 at 9:40 AM, Kenneth Marshall <<a href="mailto:ktm@rice.edu">ktm@rice.edu</a><br>
> ><mailto:<a href="mailto:ktm@rice.edu">ktm@rice.edu</a>>> wrote:<br>
> ><br>
> > On Thu, Jul 02, 2009 at 09:15:03AM -0400, SashaB wrote:<br>
> > > Hello all,<br>
> > ><br>
> > > This is a long post with a lot of info since I thought you should<br>
> > know as<br>
> > > much as possible about these NS before (a) having to ask the obvious<br>
> > > questions and (b) so you can offer suggestions.<br>
> > ><br>
> > > Here's the situation. I have set up the NS for our domains (on<br>
> > four servers)<br>
> > > and nearly all resolving properly to the domains to which they<br>
> > point. (For<br>
> > > those few that are not, I have figured out and corrected the<br>
> > issue; now<br>
> > > we're waiting for the changes to propogate.)<br>
> > ><br>
> > > However, we I have a specific domain registered via a registrar<br>
> > in the EU<br>
> > > for one of our mail/webmail servers and, each time I try to<br>
> > change the NS<br>
> > > (domain 'owners' can modify their own DNS on the registrar's site<br>
> > similar to<br>
> > > (but far simpler than) GoDaddy's "Total DNS"), I get the<br>
> > following errors:<br>
> > ><br>
> > > ns1.maildomain.eu --->"The given nameservers return different<br>
> > SOA entries."<br>
> > > ns2.maildomain.eu --->"Connection to server failed."<br>
> > ><br>
> > > Before providing your help, you should know the following:<br>
> > ><br>
> > > 1) The nameservers are shared by other NS, all of which have<br>
> > domain names<br>
> > > associated for their specific purposes. (For example:<br>
> > <a href="http://ns1.foodomain.net" target="_blank">ns1.foodomain.net</a> <<a href="http://ns1.foodomain.net" target="_blank">http://ns1.foodomain.net</a>>,<br>
> > > <a href="http://dns1.thisdomain.com" target="_blank">dns1.thisdomain.com</a> <<a href="http://dns1.thisdomain.com" target="_blank">http://dns1.thisdomain.com</a>>,<br>
> > ns1.maildomain.eu, etc.). I've pointed all "ns1"<br>
> > > domains to one IP address on each server and "ns2" are pointed to a<br>
> > > different IP address on each server but share the same IP address<br>
> > on that<br>
> > > server, etc.<br>
> > > 2) The NS for this domain are on different servers in the same<br>
> > region and<br>
> > > located in entirely different datacenters.<br>
> > > 2) While there is a master record for the ccTLD itself on its<br>
> > resident<br>
> > > server, I've also set up a separate master record for the NS1 so<br>
> > I can see<br>
> > > updating serial numbers for just the NS. Because I also set up, as a<br>
> > > supermaster, the hostname for the servers on which each of their<br>
> > NS has its<br>
> > > master record, without creating each NS as a slave on the master<br>
> > server for<br>
> > > that record, they each show on the other server as a slave and<br>
> > their serial<br>
> > > numbers (and my logs, which I've set up to view by secure<br>
> > webserver) show<br>
> > > they have been updating regularly.<br>
> > > 3) Websites and other applications, some with the same NS IP (but<br>
> > different<br>
> > > domain name), are resolving correctly.<br>
> > > 3) All NS point to IP addresses, not CNAMEs or redirects. In<br>
> > fact, I tend to<br>
> > > use IP addresses over hostnames because they resolve better if we<br>
> > make DNS<br>
> > > changes to hostnames.<br>
> > > 4) I 'played around' with the NS to learn how pdns works and<br>
> > determine how<br>
> > > best to set them up, especially for security and convenience. In<br>
> > that<br>
> > > process, I found it was just easier to point the NS for all of<br>
> > our domains<br>
> > > to the same IPs on each server and use other IPs for other<br>
> > purposes (like<br>
> > > pointing a domain's webservers to). So, I changed the IP<br>
> > addresses for the<br>
> > > NS, deleted and recreated NS records, updated SOA records, etc.<br>
> > That may<br>
> > > affect the SOA entries.<br>
> > > 5) The NS have been live for at least 24 hours each.<br>
> > > 6) The NS point to different IPs from the domain's other records,<br>
> > like the<br>
> > > MX and webmail server, which have their own IP addresses. I've<br>
> > configured my<br>
> > > virtual hosts in apache accordinly (except I did not create any<br>
> > for the NS.)<br>
> > > 7) The SOA record of NS record on each server points to the<br>
> > appropriate IP<br>
> > > address and is configured, "ns1.maildomain.eu<br>
> > > <a href="http://hostmaster.masterrecordserver.com" target="_blank">hostmaster.masterrecordserver.com</a><br>
> > <<a href="http://hostmaster.masterrecordserver.com" target="_blank">http://hostmaster.masterrecordserver.com</a>>". Since each is on<br>
> > different servers, the<br>
> > > "hostmaster" domain name is for that server, not the master<br>
> > server (ns1) of<br>
> > > the domain itself.<br>
> > > 8) I've given the registrar's IP address access to my server (via<br>
> > > hosts/csf.allow and the firewall) and added its network address<br>
> > to the<br>
> > > 'axfr' setting in pdns.conf. The pdns-recursor is not active on<br>
> > one server<br>
> > > (configuration issues) but is on the other. On the server with<br>
> > pdns-recursor<br>
> > > running, each master record has a corresponding "in-address.arpa"<br>
> > entry. I'm<br>
> > > still working on that for the other server. Neither server,<br>
> > however, is<br>
> > > experiencing resolution issues with the domains not associated<br>
> > with these in<br>
> > > question.<br>
> > ><br>
> > > So, that all said, I have a few questions that might be a source<br>
> > of some<br>
> > > issues:<br>
> > ><br>
> > > 1) I've taken the extra step of creating an "A" record for each<br>
> > NS in the<br>
> > > domain's DNS settings on the registrar's site as well as updating<br>
> > the other<br>
> > > records for the domain in the registrar's DNS as well, thinking<br>
> > that may<br>
> > > help. Will that affect the SOA records?<br>
> > > 2) Do the changes I've made to the master records, i.e., changing<br>
> > the IP<br>
> > > address of the NS several times before deciding on a final<br>
> > configuration,<br>
> > > cause such problems? (The NS for my websites, which have totally<br>
> > different<br>
> > > NS, in part, so we don't have these issues with them, have been<br>
> > 'cast in<br>
> > > stone' for several weeks and haven't changed so they're resolving<br>
> > > correctly.)<br>
> > > 3) My understanding is that mysql acts as recursor when<br>
> > pdns-recursor. How<br>
> > > can I tell if the records in mysql are correct? (I've looked at<br>
> > the records<br>
> > > via Webmin but they don't contain full record entries or have IP<br>
> > numbers<br>
> > > associated, so I can't tell how accurate they are.)<br>
> > > 4) How does pdns-recursor and rDNS configuration affect<br>
> > resolution? Could<br>
> > > that be part of the issue?<br>
> > ><br>
> > > Finally, I've done searches online and found that others have<br>
> > this issue<br>
> > > with EU-based registrars. Ostensibly, this is to prevent NS<br>
> > > misconfiguration. But, I'm finding pdns is pretty good at that so<br>
> > I'm not<br>
> > > understanding the problem. But, since I have three more domains<br>
> > with this<br>
> > > registrar, I've got to so I can fix it. Please provide your<br>
> > > solutions-oriented assistance in trying to ressolve this issue so<br>
> > we can use<br>
> > > our own NS for our mail/webmail servers.<br>
> > ><br>
> > > If you've read this far, thank you and I look forward to your help.<br>
> > ><br>
> > > Sasha<br>
> ><br>
> > Hi Sasha,<br>
> ><br>
> > Thank you for the detailed description, but I think that the problem<br>
> > is described correctly by the error message you received from your<br>
> > domain registrar:<br>
> ><br>
> > your nameservers have different SOA records (paraphrasing)<br>
> ><br>
> > All nameservers for a domain, by definition should have and serve<br>
> > identical content. I think that once you fix this inconsistancy it<br>
> > will all work.<br>
> ><br>
> > Regards,<br>
> > Ken<br>
> ><br>
> ><br>
> ><br>
> >------------------------------------------------------------------------<br>
> ><br>
> >_______________________________________________<br>
> >Pdns-users mailing list<br>
> ><a href="mailto:Pdns-users@mailman.powerdns.com">Pdns-users@mailman.powerdns.com</a><br>
> ><a href="http://mailman.powerdns.com/mailman/listinfo/pdns-users" target="_blank">http://mailman.powerdns.com/mailman/listinfo/pdns-users</a><br>
> _______________________________________________<br>
> Pdns-users mailing list<br>
> <a href="mailto:Pdns-users@mailman.powerdns.com">Pdns-users@mailman.powerdns.com</a><br>
> <a href="http://mailman.powerdns.com/mailman/listinfo/pdns-users" target="_blank">http://mailman.powerdns.com/mailman/listinfo/pdns-users</a><br>
><br>
</div></div>_____________________________________<br>
New things are always on the horizon.<br>
<div><div></div><div class="h5">_______________________________________________<br>
Pdns-users mailing list<br>
<a href="mailto:Pdns-users@mailman.powerdns.com">Pdns-users@mailman.powerdns.com</a><br>
<a href="http://mailman.powerdns.com/mailman/listinfo/pdns-users" target="_blank">http://mailman.powerdns.com/mailman/listinfo/pdns-users</a><br>
</div></div></blockquote></div><br>