BIND transfer garbled
I'm in the process of setting up a new BIND server as a secondary, in order to replace an antiquated one.
Both master and slave are running BIND 9.9.2 Transfers are occurring - sorta. They're coming through garbled. What should be coming through looking like: Code:
$ORIGIN AfricaBound.org. Code:
+–AfricaboundorgÍî¶g–Africaboundorgns1sustainablesourcescomns2sustainablesourcescomns3sustainablesourcescomG–wwwAfricaboundorgns1sustainablesourcescom Any ideas as to what's causing this and how to fix it? Thanks! |
Hi,
Could be a network problem, like a broken router, switch, firewall or something like that. What happens if you're doing the transfer manually for both udp/tcp? Code:
dig -t axfr AfricaBound.org @x.x.x.x +notcp |
Quote:
|
Aha. For bind 9.9.0 the slave zones are stored in raw format (see towards the end here)
If you want to see the zone in readable form you can run: Code:
named-compilezone -j -f raw -o zone.txt AfricaBound.org /path/to/slave/zonefile |
Quote:
Unfortunately, running that code (with the correct path, of course) gives me "not loaded due to errors." in all the variations I've tried. But at least that gives me a jumping off point. Where did you get the code above? Perhaps there's some tweaking I can do to adjust it so I can read it as a human. |
Quote:
Code:
$ named-checkzone -d -f text -o zone.txt africabound.org /var/named/hosts/slave/ l Code:
oading "africabound.org" from "/var/named/hosts/slave/" class "IN" |
Quote:
Regards |
All times are GMT -5. The time now is 07:03 PM. |