From: Suman Nath (sknath@cmu.edu)
Date: 02/02/03
You should use the dns server line in the oa.cfg file.
I have tried to resolve your dsan names, and those were resolved correctly
(I got soem non 127.0.0.1 IP).Probably your local nameserver has cached the
old mappings.
If you still have the problems, try this: add the line "nameserver
128.2.206.1" as the first line of the /etc/resolve.conf file.
-----Original Message-----
From: owner-irisnet-course@intel-iris.net
[mailto:owner-irisnet-course@intel-iris.net]On Behalf Of James Newsome
Sent: Saturday, February 01, 2003 7:49 PM
To: irisnet-course@intel-iris.net
Subject: Re: dns
I used the workaround proposed by Suman, and deleted the dns server line
from oa.cfg. However, my machine still resolves the relevant IPs to
10.212.3.33. I used dig to check the dsan.net server, and it has the
correct IP.
Apparently the DNS server I am using is caching the old value. Is there a
way to fix this?
Thanks,
Jim
On Sat, 1 Feb 2003, mukesh agrawal wrote:
>
> Short answer: The problem is the "dns server" line in the oa.cfg file.
> Delete it (or comment it out), and your troubles will go away.
>
> Long answer:
>
> In order to update DNS, the OA has to send the new information to a DNS
> server. The "DNS server" line tells the OA the IP address of the DNS
> server to contact. Unfortunately, the value that's in the oa.cfg file
> seems to be incorrect. It does not match the address of the nameserver
> that is responsible for answering queries for dsan.net.
>
> When you delete the "dns server" line, the software that's responsible for
> updating DNS figures out which DNS server to contact automatically.
>
> > According to the project description document, when we do the 'addfile'
> > command, DNS should be updated appropriately. Is this true? It does not
> > appear to be happening. In my xml file I have owner-sensor set to my own
> > IP, but DNS doesn't seem to be changed.
> >
> > At this point, CannedQueries is failing because it can't contact the
right
> > server (WH.CMU.Oakland.jnewsomePTROOT.dsan.net), which resolves to
> > 10.212.3.33. This appears to be a default, as any_random_string.dsan.net
> > resolves to the same IP.
>
>
>
This archive was generated by hypermail 2.1.5 : 06/10/04 EDT