현1116; CentOS 71012; 1060;용Ȣ16;여 웹서버를 구축Ȣ16;/140;합니다.

 

1060;용 환ᅆ1;1008; 

- VMWare 가상환ᅆ1;에 CentOS 7설치.120;

- CentOS에서 네트워크 1217;속 가능 확1064;

 

1060;며,

 

1613;상1008;

- yum 1217;속 안.120;

- 0120;러리스트 1221;상1201; ᄸ1;신.120;

- 0120;러리스트에 포함.108; 0120;러사1060;트 1452;소를 웹 브라우1200;에 1077;/141; 시 ftp 1221;상 1217;속.120;

- vi /etc/yum.repos.d/centos-base.repo에서 baseurl1012; 다1020;카카오/196; 수1221;해도 안.120;

- DNS를 KT, 구글  1228;공Ȣ16;lj16; DNS 모.160; 효과 없1020;
(애초에 다1020;카카오 0120;러1452;소를 1060;용Ȣ16;여 ftp 1221;상 1217;속.104;lj16;,163;1004;/196; 보아 DNS 문1228;lj16; 아닌 ,163;1004;/196; 판단1473;)

 

추가1201;1004;/196;

- 호스트 OSlj16; ESXi 사용 1473;

핑테스트

- 구글(google.com) - .120;

- 다1020;카카오 0120;러 - 무1025;NJ13;(1060;,148; 그럴 수 도 1080;,192;다 dz10;네요.)

 

1060;,163; ǐ12;문에 1060;틀ᇼ1;안 1652;도가 1204;혀 안나가네요 ㅠㅠ

 

아래lj16; 에러메시1648;1077;니다..

[root@sponbbang ~]# yum update

Loaded plugins: fastestmirror, langpacks

Loading mirror speeds from cached hostfile

 One of the configured repositories failed (Unknown),

 and yum doesn't have enough cached data to continue. At this point the only

 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working

        upstream. This is most often useful if you are using a newer

        distribution release than is supported by the repository (and the

        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled

            yum --disablerepo= ...

     4. Disable the repository permanently, so yum won't use it by default. Yum

        will then just ignore the repository until you permanently enable it

        again or use --enablerepo for temporary usage:

            yum-config-manager --disable

        or

            subscription-manager repos --disable=

     5. Configure the failing repository to be skipped, if it is unavailable.

        Note that yum will try to contact the repo. when it runs most commands,

        so will have to try and fail each time (and thus. yum will be be much

        slower). If it is a very temporary problem though, this is often a nice

        compromise:

            yum-config-manager --save --setopt=.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again