[Dnsmasq-discuss] Wildcard DNS on amazon EC2 instance

Simon Kelley simon at thekelleys.org.uk
Mon Nov 16 21:42:06 GMT 2015


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256



On 12/11/15 12:09, Lorenz Vanthillo wrote:
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> I have OpenShift v3 installed on an Amazon EC2 instance. It's not a
>  problem when you don't know OpenShift to answer this question.
> OpenShift contains a router and routes which makes it possible to
> access services by their hostname (for example www.example.com).
> 
> 
> In my initial configuration I was working like this:
> 
> 
> I linked a service and a hostname.On my own PC (not the server), I
> edited /etc/hosts and added the following:
> 
> 
> 52.18.247.x myapp.apps.example.com
> 
> 
> 52.18.247.x is my public IP of the amazon instance. This was
> working. So I could acces myapp.apps.example in my browser. But I
> knew this was not the best way to do it. So I wanted to set up a
> Wildcard for resolving this issue. I cleared my /etc/hosts on my
> real pc and went into my amazon instance:
> 
> 
> yum install dnsmasq
> 
> 
> dnsmasq is running on port 53.
> 
> 
> vi /etc/dnsmasq.conf
> 
> 
> add:
> 
> 
> address=/apps.example.com/52.18.247.x
> 
> 
> Than I did a restart:
> 
> 
> sudo service dnsmasq restart
> 
> 
> But it is not working and I cannot visit my services (apps) in my
> browser. What am I doing wrong?
> 
> 
> 



Your real pc, where you are running your browser, is not using the
dnsmasq you created on your amazon instance for DNS resolution. Try
setting the DNS server on your PC to point to the
Amazon instance.

Cheers,

Simon.





> 
> 
> _______________________________________________ Dnsmasq-discuss
> mailing list Dnsmasq-discuss at lists.thekelleys.org.uk 
> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBCAAGBQJWSk2tAAoJEBXN2mrhkTWibfQQAJbc4Q3I5J6JEOS5N+P/veRU
aYX0963879XIO9CtK0xLX/BFHDr416SG8Yfha80FY0EMnQFEOK6Bd8fYMjPedJAR
TBU1uADfZu8r0LUoGZFs703halK18iBF7LgeTKA0tdw1H3UaAEeqcaAFKQaiAdBz
y8TB8aJ7/nT8SFbt1DpGolsMx/1Y8uRO2hHX4e8cHFrVJsincIer6Et+DdrVvWyM
y7D6JVy3O2+7J2iwZ/QTVXFdJIBt0KEZRx8npTh0HiOUHbPQW3hyX/yZSRTFslg2
cwDPSHQVMQCgA1fwkveV+DQfszuo3tE1reoPJQA+byo/VwnwYpheh5YNZU19kBW1
kFh2v1Uy6xfiXHOqeGtJq994MmSK/zj46mhkhf0zrzCAsfiXC04xQrzKQ6CdsRnr
wQp7vvJ7gg27ggjcEEtmz21XACZMersKVQddVqoy5jwRg9gi64JHRKZY7Qp3AquB
xyKooBM29nKe8jNC1+XeII1Geek/7U4LNYbx1W8ABBBfjCjfof4ymm3GEewVbO1A
Sfi+sFnSzUJdx6+vAIzQxHUgz4HHGphIZPa3h/wqXuD6AEmAFX+cCuJ/kfPUt5qg
nT7gxiZWZ5MbzMvL+1ApsJgpJuL11XnYw2YvbiLvz0d4p/MI4xNNMFqDxzCl5ox7
1PgvNqiAg202Gi6ei5cZ
=QCD1
-----END PGP SIGNATURE-----



More information about the Dnsmasq-discuss mailing list