RE: Secure Login Problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, 2004-08-07 at 02:19, Alexander Valdez wrote:
> used dig we1.client2.attbi.com and got:
>  
> ; <<>> DiG 9.2.3 <<>> we1.client2.attbi.com
> ;; global options:  printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 270
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
>  
> ;; QUESTION SECTION:
> ;we1.client2.attbi.com.         IN      A
>  
> ;; AUTHORITY SECTION:
> client2.attbi.com.      566     IN      SOA     ns0.ipsvc.net.
> hostmaster.ipsvc.net. 1 1800 600 604800 3600
>  
> ;; Query time: 24 msec
> ;; SERVER: 192.168.0.1#53(192.168.0.1)
> ;; WHEN: Fri Aug  6 23:04:05 2004
> ;; MSG SIZE  rcvd: 99
>  
> Also asked comcast if we1.client2.attbi.com was a valid server.
> I was told it was a valid router address.
> 
> my resolv.conf is always
> ; generated by /sbin/dhclient-script
> search we1.client2.attbi.com
> nameserver 192.168.0.1
> 
> This file seems to be overwritten on boot up because I'm using
> DCHP to get my server and IP address automatically.
> 
> nslookup we1.client2.attbi.com returns:
> 
> Server:         192.168.0.1
> Address:        192.168.0.1#53
>  
> ** server can't find we1.client2.attbi.com: NXDOMAIN
>  
> Thanks for your help
> 
> Alex
> 

Well now I am confused.  I thought you were trying to resolve
ws2.harrisdirect.com no we1.client2.attbi.com.

And the reason I was thinking your resolv.conf was not correct is that
normally 192.168 network addresses (which are part of the private
address space specified in RFC 1918) are used on your LAN segment not on
DNS servers owned by ISPs.  

On my network I have my laptop get its network information via DHCP. 
This is pulled from a WRT54G linksys router.  It supplies not only the
IP address, default gateway, subnet mask, but the DNS information as
well.  If you have a router on you network connecting you to the cable
modem check its configuration.  

I still think your nameserver information is incorrect and that is what
is causing the problem.

-- 
Scot L. Harris <webid@xxxxxxxxxx>



[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux