DNS Failure guets resolved #64

New issue

Open

opened 2020-10-23 07:10:09 +00:00 by rafael · 0 comments

rafael commented

2020-10-23 07:10:09 +00:00

(Migrated from gitlab.privaz.io)

There was a DNS failure yesterday, with upstream gateway broken.

Then when www.google.com was searched, upstream would fail, and then the search prefixes would kick in:

first vpc.vtk.lan and then vtk.lan

vtk.lan would then be resolved to the lbs.

so, the result was that when searching www.google.com, www.google.com.vtk.lan would be returend pointing at the lbs.

this has obvious implications for email, proxy, etc.

As a consequence, when pointing a whole domain to a single IP (lbs), that domain cannot be part of the search list.

There was a DNS failure yesterday, with upstream gateway broken. Then when www.google.com was searched, upstream would fail, and then the search prefixes would kick in: first vpc.vtk.lan and then vtk.lan vtk.lan would then be resolved to the lbs. so, the result was that when searching www.google.com, www.google.com.vtk.lan would be returend pointing at the lbs. this has obvious implications for email, proxy, etc. As a consequence, when pointing a whole domain to a single IP (lbs), that domain cannot be part of the search list.