Ton,
It ended up being the IP in the "master" field of the domains table. I
had previously done some testing over a private network, after which I
moved it to the public side. The IP recorded in the master field was
still the private IP, so it was refusing updates from the new IP.
Thanks for the assistance! I think we're rocking now.
Ton van Rosmalen wrote:
Hi Lee,
Lee Huffman schreef:
It looks like I may have been incorrect. Things blew up on me last
night after I switched everything over. Our shared hosting server is
sending notifies properly..
named[12308]: zone X.com/IN/external: sending notifies (serial
2009032809)
But on ns1 I'm seeing the following..
pdns[2365]: Received NOTIFY for X.com from X.201.44.3 which is not a
master
Yet our shared hosting machine is listed in the supermasters table..
mysql> select * from pdns.supermasters;
+-------------+---------------------+---------+
| ip | nameserver | account |
+-------------+---------------------+---------+
| X.201.44.3 | X.com | NULL |
+-------------+---------------------+---------+
1 row in set (0.00 sec)
Any ideas why this would be taking place? I'm really at a loss as to
where I've gone wrong at this point.
I have the following entry in my supermasters table
+---------------+--------------------+----------+
| ip | nameserver | account |
+---------------+--------------------+----------+
| <supermaster ip> | <primary ns as in SOA> | internal |
+---------------+--------------------+----------+
In your case, I think, the only change necessary is the nameserver-field
needs to be adjusted
to the name of the primary nameserver as it exists in the SOA-record e.g.
ns1.X.com
Hope this solves your issue.
Regards,
Ton
_______________________________________________
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users
