On Thu, 21 Jun 2018 at 19:45, Willy Tarreau <[email protected]> wrote: > Oh indeed I didn't even notice! The correct solution is to use the > example.com domain for this, as explained in RFC2606/6761. No other > domain possibly pointing to a valid location now or in the future > should appear in test nor example files
[Gmail on mobile; forgive any formatting fubar] Example\.com resolves. There's a "you can use this domain in documentation" site there. *Someone* is absorbing the traffic to that domain - I suggest not putting it in .vtc files :-) I think the same RFC reserves .invalid as a TLD. Perhaps missing.haproxy.invalid for when a DNS entry needs not to exist, and ... something else for when it needs a real backend? I'm out of ideas on that 2nd use case ... J > -- Jonathan Matthews London, UK http://www.jpluscplusm.com/contact.html
