Challenge 11

[esalguer]

for 11 i cant seem to restart the nginx service ive already changed he config files assigned the right port number but when it comes to restarting it i keep getting the following error unable to resolve host ctf-vm: Temporary failure in name resolution

[jleiv01]

@esalguer This is due to challenge 9.
Fix the issue and it will work afterwards.

[esalguer]

ive changed it now but still the same error

[rishabkumar7]

@esalguer did you restart the service for challenge 9?

[esalguer]

cant run any restart command get the same error

[esalguer]

for 9 i changed nameserver to whatever the local host is not sure if thats correct

[esalguer]

@rishabkumar7 any ideas kinda stuck on this one

[rishabkumar7]

@esalguer this for challenge 9: were you able to look at the backup config? and restore it?

[rishabkumar7]

@esalguer I already double checked, if you solve the challenge 9, everything works.

ctf_user@ip-10-0-1-184:~$ sudo systemctl restart nginx
sudo: unable to resolve host ip-10-0-1-184: Temporary failure in name resolution
[sudo] password for ctf_user:
ctf_user@ip-10-0-1-184:~$ sudo nano /etc/resolv.conf
ctf_user@ip-10-0-1-184:~$ sudo systemctl restart nginx

[esalguer]

let me try again ive already changed both the main and config files set the correct namerserver

[esalguer]

Hi still not working i have no idea what am doing wrong

[jleiv01]

Hi still not working i have no idea what am doing wrong

Post your resolve file output

Let's see what it has.

[esalguer]

This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).

Do not edit.

This file might be symlinked as /etc/resolv.conf. If you're looking at

/etc/resolv.conf and seeing this text, you have followed the symlink.

This is a dynamic resolv.conf file for connecting local clients to the

internal DNS stub resolver of systemd-resolved. This file lists all

configured search domains.

Run "resolvectl status" to see details about the uplink DNS servers

currently in use.

Third party programs should typically not access this file directly, but only

through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a

different way, replace this symlink by a static file or a different symlink.

See man:systemd-resolved.service(8) for details about the supported modes of

operation for /etc/resolv.conf.

nameserver 127.0.0.1
options edns0 trust-ad
search xt1s3h24erne1mgxkpd32jpjoc.zx.internal.cloudapp.net

this is the output

[rishabkumar7]

can you do a cat on /etc/resolv.conf

[esalguer]

Hi this is the output when i run cat on /etc/resolv.conf

nameserver 127.0.0.1
options edns0 trust-ad
search xt1s3h24erne1mgxkpd32jpjoc.zx.internal.cloudapp.net