Mailinglist Archive: opensuse (5130 mails)
| < Previous | Next > |
RE: Re: [SLE] Upgrading SuSE enterprise from 9.0 to 9.x
- From: "Duzenbury, Rich" <RDuzenbury@xxxxxxxxxx>
- Date: Fri, 5 May 2006 13:06:17 -0500
- Message-id: <3DAC99C5454B4647BCD656A59765F026D1DF2B@xxxxxxxxxxxxxxxxxxxx>
Hi Per,
That's what I thought, too. SLES 9 has a change from SLES 8 where any queries to a resolve a host name with the suffix .local are sent to 224.0.0.251 via protocol mdns. It's listed in the release notes for the release:
"Change in Resolver Library
Incompatible change: the resolver library treats the .local top level domain as link-local domain and sends multicast DNS requests to the multicast address 224.0.0.251 port 5353 instead of normal DNS requests.
If you already use the .local domain in your nameserver configuration you will have to switch to another domain name. See http://www.multicastdns.org for more information on multicast DNS."
Well, we have a .local domain, and it's unlikely that it will be changed. I understand from some googling that SLES 9 Service Pack 1 and later respect a flag in /etc/host.conf called 'mdns off', which will revert to the correct behavior of respecting the name servers listed in /etc/resolve.conf.
I have all of the downloadable updates installed on the recalcitrant machine, and it doesn't respect the 'mdns off' setting. Accordingly, I would like to install the service pack to see if that solves the problem. FWIW, I have a couple opensuse 10.0 servers that _do_ respect the 'mdns off' flag.
Currently, I have to have all hosts listed in the /etc/host file so that things like MySQL (that want to do reverse lookups, follwed by forward lookups) will function.
If you know of a way to enable the correct behavior on SLES 9, in lieu of installing the service pack, I'd definitely be interested.
Thanks.
Regards,
Rich
> -----Original Message-----
> From: Per Jessen [mailto:per@xxxxxxxxxxxx]
> Sent: Thursday, May 04, 2006 3:26 PM
> To: suse-linux-e@xxxxxxxx
> Subject: Re: [SLE] Upgrading SuSE enterprise from 9.0 to 9.x
>
> Duzenbury, Rich wrote:
>
> > I'm wondering what the proper procedure is to upgrade a SuSE
> > enterprise 9.0 box to at least 9.1 (or 9.2 or 9.whatever).
> I believe
> > I need to upgrade to get past an issue with DNS.
>
> I can't help you with the upgrade procedure, but surely a
> mere DNS problem cannot be a reason for a complete system
> upgrade? Why not just upgrade your DNS?
>
>
>
> /Per Jessen, Zürich
>
>
> --
> Check the headers for your unsubscription address For
> additional commands send e-mail to suse-linux-e-help@xxxxxxxx
> Also check the archives at http://lists.suse.com Please read
> the FAQs: suse-linux-e-faq@xxxxxxxx
>
>
>
That's what I thought, too. SLES 9 has a change from SLES 8 where any queries to a resolve a host name with the suffix .local are sent to 224.0.0.251 via protocol mdns. It's listed in the release notes for the release:
"Change in Resolver Library
Incompatible change: the resolver library treats the .local top level domain as link-local domain and sends multicast DNS requests to the multicast address 224.0.0.251 port 5353 instead of normal DNS requests.
If you already use the .local domain in your nameserver configuration you will have to switch to another domain name. See http://www.multicastdns.org for more information on multicast DNS."
Well, we have a .local domain, and it's unlikely that it will be changed. I understand from some googling that SLES 9 Service Pack 1 and later respect a flag in /etc/host.conf called 'mdns off', which will revert to the correct behavior of respecting the name servers listed in /etc/resolve.conf.
I have all of the downloadable updates installed on the recalcitrant machine, and it doesn't respect the 'mdns off' setting. Accordingly, I would like to install the service pack to see if that solves the problem. FWIW, I have a couple opensuse 10.0 servers that _do_ respect the 'mdns off' flag.
Currently, I have to have all hosts listed in the /etc/host file so that things like MySQL (that want to do reverse lookups, follwed by forward lookups) will function.
If you know of a way to enable the correct behavior on SLES 9, in lieu of installing the service pack, I'd definitely be interested.
Thanks.
Regards,
Rich
> -----Original Message-----
> From: Per Jessen [mailto:per@xxxxxxxxxxxx]
> Sent: Thursday, May 04, 2006 3:26 PM
> To: suse-linux-e@xxxxxxxx
> Subject: Re: [SLE] Upgrading SuSE enterprise from 9.0 to 9.x
>
> Duzenbury, Rich wrote:
>
> > I'm wondering what the proper procedure is to upgrade a SuSE
> > enterprise 9.0 box to at least 9.1 (or 9.2 or 9.whatever).
> I believe
> > I need to upgrade to get past an issue with DNS.
>
> I can't help you with the upgrade procedure, but surely a
> mere DNS problem cannot be a reason for a complete system
> upgrade? Why not just upgrade your DNS?
>
>
>
> /Per Jessen, Zürich
>
>
> --
> Check the headers for your unsubscription address For
> additional commands send e-mail to suse-linux-e-help@xxxxxxxx
> Also check the archives at http://lists.suse.com Please read
> the FAQs: suse-linux-e-faq@xxxxxxxx
>
>
>
| < Previous | Next > |