Re: problem with bopm

Related to this, it seems i can do this without the admin's help, by
setting up an etc/firedns.conf file with just the working nameserver ip's
in it... im sure you were about to inform me of this anyway :)

Thanks,
Brain

On Sat, 28 Feb 2004, Andy Smith wrote:

> On Sat, Feb 28, 2004 at 07:51:58PM +0000, Craig Edwards wrote:
> >
> > here is my output from dig:
> >
> > -bash-2.05b$ dig -t a 114.237.134.208.opm.blitzed.org
> >
> > ; <<>> DiG 8.3 <<>> -t 114.237.134.208.opm.blitzed.org
> > ;; res options: init recurs defnam dnsrch
> > ;; got answer:
> > ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 2
>
> This is fine.
>
> > And here is my /etc/resolv.conf
> >
> > -bash-2.05b$ cat /etc/resolv.conf
> > domain vhost.co.il
> > nameserver 127.0.0.1
> > nameserver 213.8.141.155
> > nameserver 213.8.141.156
> > nameserver 195.40.1.36
>
> So it is probably one of the other IPs listed that is not working.
>
> dig -t a 114.237.134.208.opm.blitzed.org @127.0.0.1
> dig -t a 114.237.134.208.opm.blitzed.org @213.8.141.155
> dig -t a 114.237.134.208.opm.blitzed.org @213.8.141.156
> dig -t a 114.237.134.208.opm.blitzed.org @195.40.1.36
>
> see if those all work the same..
>
>