Search Again:

Re: Installing Bind 9.3.0

From: Alan Ordway
Date: Thursday, November 4, 2004
Time: 2:18:46 pm

Thanks, I have named 9.3.0 running now.
I am running "named -4 -g" and it looks like IPv6 records, AAAA, are
still being used. Here is a copy of the output.
04-Nov-2004 15:59:08.051 starting BIND 9.3.0 -4 -g
04-Nov-2004 15:59:08.058 loading configuration from '/etc/named.conf'
04-Nov-2004 15:59:08.065 no IPv6 interfaces found
04-Nov-2004 15:59:08.065 listening on IPv4 interface lo0, 127.0.0.1#53
04-Nov-2004 15:59:08.066 listening on IPv4 interface en0, 10.9.8.7#53
04-Nov-2004 15:59:08.074 command channel listening on 0.0.0.0#953
04-Nov-2004 15:59:08.075 ignoring config file logging statement due to
-g option
04-Nov-2004 15:59:08.088 zone 10.in-addr.arpa/IN: loaded serial
2004110102
04-Nov-2004 15:59:08.090 zone 0.0.127.in-addr.arpa/IN: loaded serial
1997022700
04-Nov-2004 15:59:08.097 zone ihmc/IN: loaded serial 2004110102
04-Nov-2004 15:59:08.099 zone localhost/IN: loaded serial 42
04-Nov-2004 15:59:08.100 running
04-Nov-2004 15:59:10.117 client 10.1.35.1#54085: query:
mail.coginst.uwf.edu IN A +
04-Nov-2004 15:59:10.406 client 10.1.35.1#54086: query:
mail.coginst.uwf.edu IN A +
04-Nov-2004 15:59:10.408 client 10.1.35.1#54087: query:
mail.coginst.uwf.edu IN AAAA +


--
Alan Ordway

On Nov 4, 2004, at 3:23 PM, Men & Mice Support wrote:

> Sorry, I should have mentioned that you have to stop the existing
> named before trying this.
>
> However, I do see the problem. In BIND 9.3.0, they've changed how
> domain name syntax is checked. In version 9.2.3, the server was very
> permissive because there was no way to alter the policy. In version
> 9.3.0, the default policy is similar to the way it was in BIND 8 -
> underscores are not permitted, for example. But you can change this.
>
> Edit the file "/var/named/conf/zoneopt/ihmc.opt". Add the following
> line inside the zone statement block:
>
> check-names ignore;
>
> You may need to do this on any slave servers as well as the master
> server.
>
> Chris Buxton
> Men & Mice - Making DNS Easy
> Customer Service and Sales Engineer
>
> At 2:10 PM -0600 11/4/04, Alan Ordway wrote:
>> I didn't use the --prefix with the ./configure.
>>
>> Here is the named -g output
>>
>> 04-Nov-2004 14:03:51.451 starting BIND 9.3.0 -g
>> 04-Nov-2004 14:03:51.458 loading configuration from '/etc/named.conf'
>> 04-Nov-2004 14:03:51.463 listening on IPv4 interface lo0, 127.0.0.1#53
>> 04-Nov-2004 14:03:51.464 could not listen on UDP socket: address in
>> use
>> 04-Nov-2004 14:03:51.464 creating IPv4 interface lo0 failed;
>> interface ignored
>> 04-Nov-2004 14:03:51.464 listening on IPv4 interface en0, 10.9.8.7#53
>> 04-Nov-2004 14:03:51.464 could not listen on UDP socket: address in
>> use
>> 04-Nov-2004 14:03:51.464 creating IPv4 interface en0 failed;
>> interface ignored
>> 04-Nov-2004 14:03:51.464 not listening on any interfaces
>> 04-Nov-2004 14:03:51.472 /var/named/conf/user_after:10: couldn't add
>> command channel 0.0.0.0#953: address in use
>> 04-Nov-2004 14:03:51.472 ignoring config file logging statement due
>> to -g option
>> 04-Nov-2004 14:03:51.475 additionally listening on IPv4 interface
>> lo0, 127.0.0.1#53
>> 04-Nov-2004 14:03:51.475 could not listen on UDP socket: address in
>> use
>> 04-Nov-2004 14:03:51.475 creating IPv4 interface lo0 failed;
>> interface ignored
>> 04-Nov-2004 14:03:51.475 additionally listening on IPv4 interface
>> en0, 10.9.8.7#53
>> 04-Nov-2004 14:03:51.475 could not listen on UDP socket: address in
>> use
>> 04-Nov-2004 14:03:51.475 creating IPv4 interface en0 failed;
>> interface ignored
>> 04-Nov-2004 14:03:51.485 zone 10.in-addr.arpa/IN: loaded serial
>> 2004110102
>> 04-Nov-2004 14:03:51.488 zone 0.0.127.in-addr.arpa/IN: loaded serial
>> 1997022700
>> 04-Nov-2004 14:03:51.489 hosts/masters/ihmc-hosts:4:
>> _ldap._tcp.dc._msdcs.ihmc: bad owner name (check-names)
>> 04-Nov-2004 14:03:51.490 zone ihmc/IN: loading master file
>> hosts/masters/ihmc-hosts: bad owner name (check-names)
>> 04-Nov-2004 14:03:51.492 zone localhost/IN: loaded serial 42
>> 04-Nov-2004 14:03:51.493 running
>>
>>
>> Here is the named -g with 9.2.3
>> Nov 04 14:04:26.050 starting BIND 9.2.3 -g
>> Nov 04 14:04:26.051 using 1 CPU
>> Nov 04 14:04:26.057 loading configuration from '/etc/named.conf'
>> Nov 04 14:04:26.060 listening on IPv4 interface lo0, 127.0.0.1#53
>> Nov 04 14:04:26.061 could not listen on UDP socket: address in use
>> Nov 04 14:04:26.062 creating IPv4 interface lo0 failed; interface
>> ignored
>> Nov 04 14:04:26.062 listening on IPv4 interface en0, 10.9.8.7#53
>> Nov 04 14:04:26.062 could not listen on UDP socket: address in use
>> Nov 04 14:04:26.062 creating IPv4 interface en0 failed; interface
>> ignored
>> Nov 04 14:04:26.062 not listening on any interfaces
>> Nov 04 14:04:26.067 /var/named/conf/user_after:10: couldn't add
>> command channel 0.0.0.0#953: address in use
>> Nov 04 14:04:26.068 ignoring config file logging statement due to -g
>> option
>> Nov 04 14:04:26.079 zone 10.in-addr.arpa/IN: loaded serial 2004110102
>> Nov 04 14:04:26.081 zone 0.0.127.in-addr.arpa/IN: loaded serial
>> 1997022700
>> Nov 04 14:04:26.087 zone ihmc/IN: loaded serial 2004110102
>> Nov 04 14:04:26.089 zone localhost/IN: loaded serial 42
>> Nov 04 14:04:26.089 running
>>
>> --
>> Alan Ordway
>>
>> On Nov 4, 2004, at 12:23 PM, Men & Mice Support wrote:
>>
>>> Good question. We haven't seen such a problem. It sounds like you
>>> might have ./configure'd with a --prefix, which means named won't
>>> find named.conf - it'll look for an etc directory inside the
>>> --prefix, instead of using the default /etc.
>>>
>>> In which case, you'll also have trouble with named.pid being put in
>>> --prefix/run instead of /var/run, but this isn't important - the
>>> QuickDNS boot script on Mac OS X doesn't make use of this. (On the
>>> other hand, Apple's boot script,
>>> /System/Library/StartupItems/BIND/BIND, relies on this file being
>>> located at /var/run/named.pid.)
>>>
>>> You can fix the location of named.conf by adding another parameter
>>> to the boot script. You probably currently have:
>>>
>>> PARAMS="-4"
>>>
>>> Change this to:
>>>
>>> PARAMS="-4 -c /etc/named.conf"
>>>
>>> Or you can reconfigure (be sure to make clean before running
>>> configure) and recompile.
>>>
>>> If that's not the problem, try this command (still assuming Mac OS
>>> X):
>>>
>>> sudo named -g
>>>
>>> That should tell you what's going on.
>>>
>>> Chris Buxton
>>> Men & Mice - Making DNS Easy
>>> Customer Service and Sales Engineer
>>>
>>> At 10:17 AM -0600 11/4/04, Alan Ordway wrote:
>>>> Ok, so I did a mv /usr/sbin/named /usr/sbin/named.9.2.3 and then mv
>>>> bin/named/named /usr/sbin/named and then made sure the privileges
>>>> were correct.
>>>> I then did /Library/StartupItems/QuickDNS/named restart
>>>> Now the local domains will not resolve.
>>>> I changed the named back to the 9.2.3 version and did a restart and
>>>> local domains resolve.
>>>> What else needs to be done so that version 9.3 will resolve local
>>>> domains?
>>>>
>>>> --
>>>> Alan Ordway
>>>>
>>>> On Nov 3, 2004, at 12:51 PM, Men & Mice Support wrote:
>>>>
>>>>> At 8:31 AM -0600 11/3/04, Alan Ordway wrote:
>>>>>> Do I really NEED any components other than named?
>>>>>
>>>>> No.
>>>>>
>>>>>> So basically I run ./configure, then make, then make install
>>>>>
>>>>> No, don't run 'make install'. It will install lots of stuff in
>>>>> random locations that are not appropriate for Mac OS X.
>>>>>
>>>>> ./configure
>>>>> make
>>>>> sudo mv bin/named/named /usr/sbin/named
>>>>>
>>>>> The new copy should be given the same privileges as the old one -
>>>>> this seems to be a feature of the 'mv' command. However, just to
>>>>> be sure, you can follow up with this one:
>>>>>
>>>>> sudo chmod 755 /usr/sbin/named
>>>>>
>>>>> Chris Buxton
>>>>> Men & Mice - Making DNS Easy
>>>>> Customer Service and Sales Engineer
>>>>>
>>>>>> and then I copy the named from /usr/local/sbin to /usr/sbin and
>>>>>> replace the named that is there.
>>>>>>
>>>>>> --
>>>>>> Alan Ordway
>>>>>>
>>>>>> On Nov 2, 2004, at 6:55 PM, Men & Mice Support wrote:
>>>>>>
>>>>>>> If you set --prefix, you must also set a couple of other
>>>>>>> parameters so that the new named expects named.conf in /etc, and
>>>>>>> so that it puts run/named.pid in /var. There are a number of
>>>>>>> other parameters you could set, too (manpage location, info
>>>>>>> location, etc.).
>>>>>>>
>>>>>>> Alternatively, just './configure', and then manually install
>>>>>>> just the components you want. For example, bin/named/named goes
>>>>>>> to /usr/sbin/named.
>>>>>>>
>>>>>>> Just use the -4 option. That way, if Apple fixes this issue
>>>>>>> (assuming you're using Mac OS X), and if you should ever want
>>>>>>> IPv6 support, you won't have to recompile.
>>>>>>>
>>>>>>> Chris Buxton
>>>>>>> Men & Mice - Making DNS Easy
>>>>>>> Customer Service and Sales Engineer
>>>>>>>
>>>>>>> At 7:45 PM -0600 11/2/04, Alan Ordway wrote:
>>>>>>>> What is the best way to update Bind from 9.2.3 to 9.3.0? Should
>>>>>>>> I add a flag "--prefix=/usr" to the ./configure to have the
>>>>>>>> install replace the existing build or should I just do the
>>>>>>>> ./configure and then change the startup files to point to the
>>>>>>>> /usr/local/sbin/named?
>>>>>>>> Also should I build with IPv6 disabled or just put the -4 in
>>>>>>>> the params to fix the IPv6 problem with the root servers?
>>>>>>>>
>>>>>>>> Alan Ordway
>>>>>>>> IHMC
>
>




Messages In This Thread:



Return to Digital Point Solutions' Home Page