Hi all,
I am planning to migrate away from Bind to PowerDNS with MySQL and Geo backend,
but so far have failed. The PowerDNS part and MySQL has worked, but the geo
part didn't work. What I mean by this is that when I check from (for
example) Asia:
$ dig @203.123.59.184 www.test.com
; DiG
2009/5/13 - Simon - ken...@gmail.com:
I have a small problem with MX records. We are using Google Apps for web
application's email needs and we've already set everything up. We can now
send emails from @ourdomainname.com but we cannot receive them. To do so, we
need to change some MX records
Thank you guys, the problem was the capital letter in the .COM like
Christian mentioned. Thanks again!
Simon
On Thu, May 14, 2009 at 3:16 AM, Christian Tellnes christ...@tellnes.nowrote:
2009/5/13 - Simon - ken...@gmail.com:
I have a small problem with MX records. We are using Google Apps
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]:
On Thu, May 14, 2009 at 12:02 PM, Steven Haryanto
stevenharya...@gmail.com wrote:
Dear all,
We are getting a lot of this error:
May 14 04:57:44 x pdns[6104]: Exception: Parsing record content: while
parsing IP address, expected digits at position 0 in '.'
Solved. This is because the content
Forward to list.
Originele bericht
Onderwerp: Re: [Pdns-users] Re: Supermaster without NS records
Datum: Thu, 14 May 2009 18:10:07 +0200
Van:Ton van Rosmalen t...@netbase.nl
Aan:Lee Huffman l...@shiftedlabs.com
Referenties:4a0b7bab.6030...@shiftedlabs.com
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
