[Chester LUG] A little help DNS weirdness in Linux mint. Help required

[Robin Hemuss]

I might have completely got my wires crossed here, but I'm sure I remember 
someone telling me that Micrsoft use address 0 to refer to the network, with 
the first computer on the network being at address 1. This causes problems 
with configuration since real IP doesn't do this.

Thought I'd mention it just in case that's what's happening.

Robin


On Friday 05 June 2015 14:02:32 Stuart Burns wrote:
> Hi Everyone,
> 
> I decided to make the jump from Windows 7 to Linux Mint rather than end up
> on the MS pay to play that is coming with Windows 10 in year 2 (I kid you
> not!)
> 
> Anyhow, for the most part the install went ok (There was some docking
> station weirdness but turning it off and on again fixed it. Go figure)
> 
> Anyhow, the real problem is the DNS. I have set up my DHCP client so it
> gets it's address automatically.
> 
> I am able to resolve my internal hosts without issue..
> thinkpad stuart # nslookup
> > vc
> Server:        192.168.0.201
> Address:    192.168.0.201#53
> 
> Name:    vc.test.local
> Address: 192.168.0.204
> 
> External works fine..
> 
> > linux.org
> Server:        192.168.0.201
> Address:    192.168.0.201#53
> 
> Non-authoritative answer:
> Name:    linux.org
> Address: 107.170.40.56
> 
> 
> However, when trying to connect to an internal URL using the FQDN mentioned
> above, I get a timeout about not being able to resolve the address. Well
> weird. I have checked in Firefox and it is set to direct connection.
> 
> The application is up and working,  It worked without issue in Windows 7.
> Does anyone have any ideas about this weird behavior ?
> 
> It just seems that Firefox cannot resolve internal addresses but fine with
> everything else.
> 
> Regards
> 
> Stu
> 
> -- 
> Stuart Burns
> E: stuart.james.burns at gmail.com
> M: [redacted]
>